Lime  Version 9.19.2   Pre-release     12-December-2025.
==================================.

Verified on Windows XP to Windows 10 (&11)  and on MacOS Tiger (10.4) to Mojave (10.14).
Lime will NOT work on Mac OSX 10.15 or later because Apple has, unhelpfully, dropped support for 32 bit apps.
Fortunately, Microsoft has not been so stupid.


If updating to 9.19, if not already there, copy this folder to your 32 bit applications program files folder:
On 32 bit Windows  C:/Program Files/Lime/Lime 9.17
On 64 bit Windows  C:/Program Files (x86)/Lime/Lime 9.17


Lime 9.17 was the Unicode version of Lime; Lime 9.18 & 9.19 were the next releases.  Text in all annotations use Unicode,
so there should be no more incompatibilities when a score is moved from a Mac to Windows or vice versa.
There was a small enhancement to the Lime file format to accomodate new features.  By and large the 9.19.1 format
is readable by 9.17 and later.


Many scores, created prior to 9.17 will have non-unicode annotations, using their local code page
(character set).  By and large, on Windows, the annotations were flagged with the code page,
so translation to Unicode is straightforward.

Unfortunately there was an 'undocumented feature' in Windows' Lime prior to 9.17.  If a text annotation
(e.g. title, composer, etc) were entered using a simple text assistant dialog (e.g. title, composer, etc),
the character set was set to the default.  The annotation would use the default locale code page of the host
machine. If the annotation were basic ASCII, there was no problem.  However, if it were foreign text
(Greek, Russian, Hebrew, Arabic, etc), it would display fine on any Windows computer that defaulted to that
character set, but not on any other (and not on Macs).  The same issue applies to part and context names.

When converting such annotations to Unicode, Lime 9.17 needs to be told what the originating character set was.
Otherwise they can become garbage. This applies to both Windows and Macs.  When you first read an older file,
you will be prompted to specify what the default code page to use is.  See section 3.2.1 of the Manual Addendum.


The fonts required by Lime (Marl, Tufa, etc), should be in the same folder as the Lime executable
(or, on Macs, embedded in the application package).  If you need to use them outside of Lime,
they will need to be need to be installed on your system.  You should always install the latest versions.


Basic Lime is now 'donation-ware'.  Anyone who previously purchased it, is deemed to have 'donated'.
Donations, which go towards the development of facilities for blind and partially sighted musicians,
may be made on the main Lime web site  (www.)cerlsoundgroup.org
Those who have donated will receive a registration key.  Once this has been entered,
the initial splash page that is displayed when Lime starts up will no longer appear.
All basic Lime facilities are available, whether or not you have donated.

----------------------------------------------------------------------------
